Periodic channel state information (CSI) reporting using a physical uplink control channel (PUCCH)

ABSTRACT

Technology for a user equipment (UE) to report periodic channel state information (CSI) is disclosed. The UE can generate a plurality of CSI reports for serving cells for transmission in a subframe. Each CSI report can correspond to a physical uplink control channel (PUCCH) reporting type among a plurality of CSI processes having a CSI process index (CSIProcessIndex) and a serving cell index (ServCellIndex). The UE can determine different priorities corresponding to each of the plurality of PUCCH reporting types. The UE can drop CSI reports corresponding to all CSI processes except a CSI process having the lowest CSIProcessIndex. The UE can drop CSI reports corresponding to all ServCellIndexes except a CSI report with the lowest ServCellIndex. The UE can multiplex at least one non-colliding CSI report from among CSI reports that are not dropped and hybrid automatic repeat request-acknowledgement (HARQ-ACK) feedback bits for transmission to an eNodeB.

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/145,112, filed Dec. 31, 2013, which is a continuation of U.S. patentapplication Ser. No. 13/688,794, filed Nov. 29, 2012, which claims thebenefit of and hereby incorporates by reference U.S. Provisional PatentApplication Ser. No. 61/679,627, filed Aug. 3, 2012, each of which areincorporated by reference in their entirety.

BACKGROUND

Wireless mobile communication technology uses various standards andprotocols to transmit data between a node (e.g., a transmission station)and a wireless device (e.g., a mobile device). Some wireless devicescommunicate using orthogonal frequency-division multiple access (OFDMA)in a downlink (DL) transmission and single carrier frequency divisionmultiple access (SC-FDMA) in an uplink (UL) transmission. Standards andprotocols that use orthogonal frequency-division multiplexing (OFDM) forsignal transmission include the third generation partnership project(3GPP) long term evolution (LTE), the Institute of Electrical andElectronics Engineers (IEEE) 802.16 standard (e.g., 802.16e, 802.16m),which is commonly known to industry groups as WiMAX (Worldwideinteroperability for Microwave Access), and the IEEE 802.11 standard,which is commonly known to industry groups as WiFi.

In 3GPP radio access network (RAN) LTE systems, the node can be acombination of Evolved Universal Terrestrial Radio Access Network(E-UTRAN) Node Bs (also commonly denoted as evolved Node Bs, enhancedNode Bs, eNodeBs, or eNBs) and Radio Network Controllers (RNCs), whichcommunicates with the wireless device, known as a user equipment (UE).The downlink (DL) transmission can be a communication from the node(e.g., eNodeB) to the wireless device (e.g., UE), and the uplink (UL)transmission can be a communication from the wireless device to thenode.

In homogeneous networks, the node, also called a macro node, can providebasic wireless coverage to wireless devices in a cell. The cell can bethe area in which the wireless devices are operable to communicate withthe macro node. Heterogeneous networks (HetNets) can be used to handlethe increased traffic loads on the macro nodes due to increased usageand functionality of wireless devices. HetNets can include a layer ofplanned high power macro nodes (or macro-eNBs) overlaid with layers oflower power nodes (small-eNBs, micro-eNBs, pico-eNBs, femto-eNBs, orhome eNBs [HeNBs]) that can be deployed in a less well planned or evenentirely uncoordinated manner within the coverage area (cell) of a macronode. The lower power nodes (LPNs) can generally be referred to as “lowpower nodes”, small nodes, or small cells.

The macro node can be used for basic coverage. The low power nodes canbe used to fill coverage holes, to improve capacity in hot-zones or atthe boundaries between the macro nodes' coverage areas, and improveindoor coverage where building structures impede signal transmission.Inter-cell interference coordination (ICIC) or enhanced ICIC (eICIC) maybe used for resource coordination to reduce interference between thenodes, such as macro nodes and low power nodes in a HetNet.

A Coordinated MultiPoint (CoMP) system may also be used to reduceinterference from neighboring nodes in both homogeneous networks andHetNets. In the CoMP system, the nodes, referred to as cooperatingnodes, can also be grouped together with other nodes where the nodesfrom multiple cells can transmit signals to the wireless device andreceive signals from the wireless device. The cooperating nodes can benodes in the homogeneous network or macro nodes and/or lower power nodes(LPN) in the HetNet. CoMP operation can apply to downlink transmissionsand uplink transmissions. Downlink CoMP operation can be divided intotwo categories: coordinated scheduling or coordinated beamforming (CS/CBor CS/CBF), and joint processing or joint transmission (JP/JT). WithCS/CB, a given subframe can be transmitted from one cell to a givenwireless device (e.g., UE), and the scheduling, including coordinatedbeamforming, is dynamically coordinated between the cells in order tocontrol and/or reduce the interference between different transmissions.For joint processing, joint transmission can be performed by multiplecells to a wireless device (e.g., UE), in which multiple nodes transmitat the same time using the same time and frequency radio resourcesand/or dynamic cell selection. Uplink CoMP operation can be divided intotwo categories: joint reception (JR) and coordinated scheduling andbeamforming (CS/CB). With JR, a physical uplink shared channel (PUSCH)transmitted by the wireless device (e.g., UE) can be received jointly atmultiple points at a time frame. The set of the multiple points canconstitute the CoMP reception point (RP) set, and can be included inpart of UL CoMP cooperating set or in an entire UL CoMP cooperating set.JR can be used to improve the received signal quality. In CS/CB, userscheduling and precoding selection decisions can be made withcoordination among points corresponding to the UL CoMP cooperating set.With CS/CB, PUSCH transmitted by the UE can be received at one point.

BRIEF DESCRIPTION OF THE DRAWINGS

Features and advantages of the disclosure will be apparent from thedetailed description which follows, taken in conjunction with theaccompanying drawings, which together illustrate, by way of example,features of the disclosure; and, wherein:

FIG. 1 illustrates a block diagram of various component carrier (CC)bandwidths in accordance with an example;

FIG. 2A illustrates a block diagram of multiple contiguous componentcarriers in accordance with an example;

FIG. 2B illustrates a block diagram of intra-band non-contiguouscomponent carriers in accordance with an example;

FIG. 2C illustrates a block diagram of inter-band non-contiguouscomponent carriers in accordance with an example;

FIG. 3A illustrates a block diagram of a symmetric-asymmetric carrieraggregation configuration in accordance with an example;

FIG. 3B illustrates a block diagram of an asymmetric-symmetric carrieraggregation configuration in accordance with an example;

FIG. 4 illustrates a block diagram of uplink radio frame resources(e.g., a resource grid) in accordance with an example;

FIG. 5 illustrates a block diagram of frequency hopping for a physicaluplink control channel (PUCCH) in accordance with an example;

FIG. 6 illustrates a table of physical uplink control channel (PUCCH)reporting types per PUCCH reporting mode and mode state in accordancewith an example;

FIG. 7A illustrates a block diagram of a homogenous network using anintra-site coordinated multipoint (CoMP) system (e.g., CoMP scenario 1)in accordance with an example;

FIG. 7B illustrates a block diagram of a homogenous network with hightransmission power using an inter-site coordinated multipoint (CoMP)system (e.g., CoMP scenario 2) in accordance with an example;

FIG. 7C illustrates a block diagram of a coordinated multipoint (CoMP)system in a heterogeneous network with low power nodes (e.g., CoMPscenario 3 or 4) in accordance with an example;

FIG. 8 depicts functionality of computer circuitry of a user equipment(UE) operable to report periodic channel state information (CSI)configured in a specified transmission mode in accordance with anexample;

FIG. 9 depicts a flow chart of a method for periodic channel stateinformation (CSI) reporting in a coordinated multipoint (CoMP) scenarioat a wireless device in accordance with an example;

FIG. 10 illustrates a block diagram of a serving node, a coordinationnode, and wireless device in accordance with an example; and

FIG. 11 illustrates a diagram of a wireless device (e.g., UE) inaccordance with an example.

Reference will now be made to the exemplary embodiments illustrated, andspecific language will be used herein to describe the same. It willnevertheless be understood that no limitation of the scope of theinvention is thereby intended.

DETAILED DESCRIPTION

Before the present invention is disclosed and described, it is to beunderstood that this invention is not limited to the particularstructures, process steps, or materials disclosed herein, but isextended to equivalents thereof as would be recognized by thoseordinarily skilled in the relevant arts. It should also be understoodthat terminology employed herein is used for the purpose of describingparticular examples only and is not intended to be limiting. The samereference numerals in different drawings represent the same element.Numbers provided in flow charts and processes are provided for clarityin illustrating steps and operations and do not necessarily indicate aparticular order or sequence.

Example Embodiments

An initial overview of technology embodiments is provided below and thenspecific technology embodiments are described in further detail later.This initial summary is intended to aid readers in understanding thetechnology more quickly but is not intended to identify key features oressential features of the technology nor is it intended to limit thescope of the claimed subject matter.

An increase in the amount of wireless data transmission has createdcongestion in wireless networks using licensed spectrum to providewireless communication services for wireless devices, such as smartphones and tablet devices. The congestion is especially apparent in highdensity and high use locations such as urban locations and universities.

One technique for providing additional bandwidth capacity to wirelessdevices is through the use carrier aggregation of multiple smallerbandwidths to form a virtual wideband channel at a wireless device(e.g., UE). In carrier aggregation (CA) multiple component carriers (CC)can be aggregated and jointly used for transmission to/from a singleterminal. Carriers can be signals in permitted frequency domains ontowhich information is placed. The amount of information that can beplaced on a carrier can be determined by the aggregated carrier'sbandwidth in the frequency domain. The permitted frequency domains areoften limited in bandwidth. The bandwidth limitations can become moresevere when a large number of users are simultaneously using thebandwidth in the permitted frequency domains.

FIG. 1 illustrates a carrier bandwidth, signal bandwidth, or a componentcarrier (CC) that can be used by the wireless device. For example, theLTE CC bandwidths can include: 1.4 MHz 210, 3 MHz 212, 5 MHz 214, 10 MHz216, 15 MHz 218, and 20 MHz 220. The 1.4 MHz CC can include 6 resourceblocks (RBs) comprising 72 subcarriers. The 3 MHz CC can include 15 RBscomprising 180 subcarriers. The 5 MHz CC can include 25 RBs comprising300 subcarriers. The 10 MHz CC can include 50 RBs comprising 600subcarriers. The 15 MHz CC can include 75 RBs comprising 900subcarriers. The 20 MHz CC can include 100 RBs comprising 1200subcarriers.

Carrier aggregation (CA) enables multiple carrier signals to besimultaneously communicated between a user's wireless device and a node.Multiple different carriers can be used. In some instances, the carriersmay be from different permitted frequency domains. Carrier aggregationprovides a broader choice to the wireless devices, enabling morebandwidth to be obtained. The greater bandwidth can be used tocommunicate bandwidth intensive operations, such as streaming video orcommunicating large data files.

FIG. 2A illustrates an example of carrier aggregation of continuouscarriers. In the example, three carriers are contiguously located alonga frequency band. Each carrier can be referred to as a componentcarrier. In a continuous type of system, the component carriers arelocated adjacent one another and can be typically located within asingle frequency band (e.g., band A). A frequency band can be a selectedfrequency range in the electromagnetic spectrum. Selected frequencybands are designated for use with wireless communications such aswireless telephony. Certain frequency bands are owned or leased by awireless service provider. Each adjacent component carrier may have thesame bandwidth, or different bandwidths. A bandwidth is a selectedportion of the frequency band. Wireless telephony has traditionally beenconducted within a single frequency band. In contiguous carrieraggregation, only one fast Fourier transform (FFT) module and/or oneradio frontend may be used. The contiguous component carriers can havesimilar propagation characteristics which can utilize similar reportsand/or processing modules.

FIGS. 2B-2C illustrates an example of carrier aggregation ofnon-continuous component carriers. The non-continuous component carriersmay be separated along the frequency range. Each component carrier mayeven be located in different frequency bands. Non-contiguous carrieraggregation can provide aggregation of a fragmented spectrum. Intra-band(or single-band) non-contiguous carrier aggregation providesnon-contiguous carrier aggregation within a same frequency band (e.g.,band A), as illustrated in FIG. 2B. Inter-band (or multi-band)non-contiguous carrier aggregation provides non-contiguous carrieraggregation within different frequency bands (e.g., bands A, B, or C),as illustrated in FIG. 2C. The ability to use component carriers indifferent frequency bands can enable more efficient use of availablebandwidth and increases the aggregated data throughput.

Network symmetric (or asymmetric) carrier aggregation can be defined bya number of downlink (DL) and uplink (UL) component carriers offered bya network in a sector. UE symmetric (or asymmetric) carrier aggregationcan be defined by a number of downlink (DL) and uplink (UL) componentcarriers configured for a UE. The number of DL CCs may be at least thenumber of UL CCs. A system information block type 2 (SIB2) can providespecific linking between the DL and the UL. FIG. 3A illustrates a blockdiagram of a symmetric-asymmetric carrier aggregation configuration,where the carrier aggregation is symmetric between the DL and UL for thenetwork and asymmetric between the DL and UL for the UE. FIG. 3Billustrates a block diagram of an asymmetric-symmetric carrieraggregation configuration, where the carrier aggregation is asymmetricbetween the DL and UL for the network and symmetric between the DL andUL for the UE.

A component carrier can be used to carry channel information via a radioframe structure transmitted on the physical (PHY) layer in a uplinktransmission between a node (e.g., eNodeB) and the wireless device(e.g., UE) using a generic long term evolution (LTE) frame structure, asillustrated in FIG. 4. While an LTE frame structure is illustrated, aframe structure for an IEEE 802.16 standard (WiMax), an IEEE 802.11standard (WiFi), or another type of communication standard using SC-FDMAor OFDMA may also be used.

FIG. 4 illustrates an uplink radio frame structure. In the example, aradio frame 100 of a signal used to transmit control information or datacan be configured to have a duration, T_(f), of 10 milliseconds (ms).Each radio frame can be segmented or divided into ten subframes 110 ithat are each 1 ms long. Each subframe can be further subdivided intotwo slots 120 a and 120 b, each with a duration, T_(slot), of 0.5 ms.Each slot for a component carrier (CC) used by the wireless device andthe node can include multiple resource blocks (RBs) 130 a, 130 b, 130 i,130 m, and 130 n based on the CC frequency bandwidth. Each RB (physicalRB or PRB) 130 i can include 12-15 kHz subcarriers 136 (on the frequencyaxis) and 6 or 7 SC-FDMA symbols 132 (on the time axis) per subcarrier.The RB can use seven SC-FDMA symbols if a short or normal cyclic prefixis employed. The RB can use six SC-FDMA symbols if an extended cyclicprefix is used. The resource block can be mapped to 84 resource elements(REs) 140 i using short or normal cyclic prefixing, or the resourceblock can be mapped to 72 REs (not shown) using extended cyclicprefixing. The RE can be a unit of one SC-FDMA symbol 142 by onesubcarrier (i.e., 15 kHz) 146. Each RE can transmit two bits 150 a and150 b of information in the case of quadrature phase-shift keying (QPSK)modulation. Other types of modulation may be used, such as 16 quadratureamplitude modulation (QAM) or 64 QAM to transmit a greater number ofbits in each RE, or bi-phase shift keying (BPSK) modulation to transmita lesser number of bits (a single bit) in each RE. The RB can beconfigured for an uplink transmission from the wireless device to thenode.

Reference signals (RS) can be transmitted by SC-FDMA symbols viaresource elements in the resource blocks. Reference signals (or pilotsignals or tones) can be a known signal used for various reasons, suchas to synchronize timing, estimate a channel, and/or noise in thechannel. Reference signals can be received and transmitted by wirelessdevices and nodes. Different types of reference signals (RS) can be usedin a RB. For example, in LTE systems, uplink reference signal types caninclude a sounding reference signal (SRS) and a UE-specific referencesignal (UE-specific RS or UE-RS) or a demodulation reference signal(DM-RS). In LTE systems, downlink reference signal types can includechannel state information reference signals (CSI-RS) which can bemeasured by a wireless device to provide CSI reports on a channel.

An uplink signal or channel can include data on a Physical Uplink SharedCHannel (PUSCH) or control information on a Physical Uplink ControlCHannel (PUCCH). In LTE, the uplink physical channel (PUCCH) carryinguplink control information (UCI) can include channel state information(CSI) reports, Hybrid Automatic Retransmission reQuest (HARQ)ACKnowledgment/Negative ACKnowledgment (ACK/NACK) and uplink schedulingrequests (SR).

The wireless device can provide aperiodic CSI reporting using the PUSCHor periodic CSI reporting using PUCCH. The PUCCH can support multipleformats (i.e., PUCCH format) with various modulation and coding schemes(MCS), as shown for LTE in Table 1. For example, PUCCH format 3 can beused to convey multi-bit HARQ-ACK, which can be used for carrieraggregation.

TABLE 1 PUCCH Modulation Number of bits per format scheme subframe,M_(bit) 1 N/A N/A 1a BPSK 1 1b QPSK 2 2 QPSK 20 2a QPSK + BPSK 21 2bQPSK + QPSK 22 3 QPSK 48

In another example, PUCCH format 2 can use frequency hopping, asillustrated in FIG. 5. Frequency hopping can be a method of transmittingradio signals by rapidly switching a carrier among many frequencychannels using a pseudorandom sequence or specified sequence known toboth a transmitter (e.g., UE in an uplink) and a receiver (e.g., eNB inthe uplink). Frequency hopping can enable the UE to exploit thefrequency diversity of a wideband channel used in LTE in an uplink whilekeeping a contiguous allocation (in the time domain).

The PUCCH can include various channel state information (CSI) reports.The CSI components in the CSI reports can include a channel qualityindicator (CQI), a precoding matrix indicator (PMI), a precoding typeindicator (PTI), and/or rank indication (RI) reporting type. The CQI canbe signaled by a UE to the eNodeB to indicate a suitable data rate, suchas a modulation and coding scheme (MCS) value, for downlinktransmissions, which can be based on a measurement of the receiveddownlink signal to interference plus noise ratio (SINR) and knowledge ofthe UE's receiver characteristics. The PMI can be a signal fed back bythe UE to support multiple-input multiple-output (MIMO) operation. ThePMI can correspond to an index of the precoder (within a codebook sharedby the UE and eNodeB), which can maximize an aggregate number of databits which can be received across all downlink spatial transmissionlayers. PTI can be used to distinguish slow from fast fadingenvironments. The RI can be signaled to the eNodeB by UEs configured forPDSCH transmission modes 3 (e.g., open-loop spatial multiplexing) and 4(e.g., closed-loop spatial multiplexing). RI can correspond to a numberof useful transmission layers for spatial multiplexing (based on theUE's estimate of the downlink channel), enabling the eNodeB to adapt thePDSCH transmissions accordingly.

The granularity of a CQI report can be divided into three levels:wideband, UE selected subband, and higher layer configured subband. Thewideband CQI report can provide one CQI value for an entire downlinksystem bandwidth. The UE selected subband CQI report can divide thesystem bandwidth into multiple subbands, where the UE can select a setof preferred subbands (the best M subbands), then report one CQI valuefor the wideband and one differential CQI value for the set (assumingtransmission only over the selected M subbands). The higher layerconfigured subband CQI report can provide a highest granularity. In thehigher layer configured subband CQI report, the wireless device candivide the entire system bandwidth into multiple subbands, then reportsone wideband CQI value and multiple differential CQI values, such as onefor each subband.

The UCI carried by the PUCCH can use different PUCCH reporting types (orCQI/PMI and RI reporting types) to specify which CSI reports are beingtransmitted. For example, PUCCH reporting Type 1 can support CQIfeedback for UE selected sub-bands; Type 1 a can support subband CQI andsecond PMI feedback; Type 2, Type 2b, and Type 2c can support widebandCQI and PMI feedback; Type 2a can support wideband PMI feedback; Type 3can supports RI feedback; Type 4 can supports wideband CQI, Type 5 cansupport RI and wideband PMI feedback; and Type 6 can support RI and PTIfeedback.

Different CSI components can be included based on the PUCCH reportingtype. For example, RI can be included in PUCCH reporting types 3, 5, or6. Wideband PTI can be included in PUCCH reporting type 6. Wideband PMIcan be included in PUCCH reporting types 2a or 5. Wideband CQI can beincluded in PUCCH reporting types 2, 2b, 2c, or 4. Subband CQI can beincluded in PUCCH reporting types 1 or 1a.

The CQI/PMI and RI (PUCCH) reporting types with distinct periods andoffsets can be supported for the PUCCH CSI reporting modes illustratedby the table in FIG. 5. FIG. 5 illustrates an example for LTE of thePUCCH reporting type and payload size per PUCCH reporting mode and modestate.

The CSI information reported can vary based on the downlink transmissionscenarios used. The various scenarios for the downlink can be reflectedin different transmission modes (TMs). For example, in LTE, TM 1 can usea single transmit antenna; TM 2 can use transmit diversity; TM 3 can useopen loop spatial multiplexing with cyclic delay diversity (ODD); TM 4can use closed loop spatial multiplexing; TM 5 can use multi-user MIMO(MU-MIMO); TM 6 can use closed loop spatial multiplexing using a singletransmission layer; TM 7 can use beamforming with UE-specific RS; TM 8can use single or dual-layer beamforming with UE-specific RS; and TM 9can use a multilayer transmission to support closed-loop single userMIMO (SU-MIMO) or carrier aggregation. In an example, TM 10 can be usedfor coordinated multipoint (CoMP) signaling, such as joint processing(JP), dynamic point selection (DPS), and/or coordinatedscheduling/coordinated beamforming (CS/CB).

Each transmission mode can use different PUCCH CSI reporting modes,where each PUCCH CSI reporting mode can represent different CQI and PMIfeedback types, as shown for LTE in Table 2.

TABLE 2 PMI Feedback Type No PMI Single PMI PUCCH CQI Wideband Mode 1-0Mode 1-1 Feedback Type (wideband CQI) UE Selected Mode 2-0 Mode 2-1(subband CQI)

For example, in LTE, TMs 1, 2, 3, and 7 can use PUCCH CSI reportingmodes 1-0 or 2-0; TMs 4, 5, and 6 can use PUCCH CSI reporting modes 1-1or 2-1; TM 8 can use PUCCH CSI reporting modes 1-1 or 2-1 if the UE isconfigured with PMI/RI reporting, or PUCCH CSI reporting modes 1-0 or2-0 if the UE is configured without PMI/RI reporting; and TMs 9 and 10can use PUCCH CSI reporting modes 1-1 or 2-1 if the UE is configuredwith PMI/RI reporting and number of CSI-RS ports is greater than one, orPUCCH CSI reporting modes 1-0 or 2-0 if the UE is configured withoutPMI/RI reporting or number of CSI-RS ports is equal to one. Based on thedownlink transmission scheme (e.g., transmission mode), a UE cangenerate more CSI reports than may be permitted to be transmitted tonodes (e.g., eNBs) without generating a signal collision orinterference. The wireless device (e.g. UE) may make a determination onthe CSI reports to keep and transmit and which CSI reports to drop ordiscard (and not transmit) to avoid a collision on a subframe.

In CSI reporting, the PUCCH format 2 can convey 4 to 11 CSI(CQI/PMI/PTI/RI) bits from the UE to the eNB. In carrier aggregation,each serving cell can be independently configured by radio resourcecontrol (RRC) signaling regarding a CSI configuration, such as aperiodicity, a starting offset, or a PUCCH mode. However, thetransmission of CSI using PUCCH format 2 may only be performed inprimary cell. In an example using PUCCH format 2, one CSI report for aspecified serving cell may be transmitted while the remaining CSIreports for other serving cells may be dropped when more than one CSIreport for multiple serving cells has a potential to collide with eachother in a same subframe. Dropping the CSI reports for other servingcells may prevent the collision of the CSI reports in the same subframe.In an example, the criteria used to determine the priority of a periodicCSI reports transmitted and the periodic CSI reports that are droppedcan be based on a PUCCH reporting type with a lower CSI reporting typepriority being dropped. PUCCH reporting types 3, 5, 6, and 2a can have ahighest or top priority, and PUCCH reporting types 2, 2b, 2c, and 4 canhave a next priority or a second priority, and PUCCH reporting types 1and 1a can have a third or lowest priority. So, the UE can drop the CSIreports with PUCCH reporting types 1, 1a, first, then drop the CSIreports with PUCCH reporting types 2, 2b, 2c, and 4, second, then dropany CSI reports with PUCCH reporting types 3, 5, 6, and 2a above thenumber of CSI report(s) to be transmitted. In an example, a CSI reportcan be generated for each component carrier (CC). Each CC can berepresented by a serving cell index (i.e., ServCellIndex). Among CSIreports having reporting types with a same priority (e.g., PUCCHreporting types 3, 5, 6, and 2a), a priority of a cell can decrease asthe corresponding serving cell index (i.e., ServCellIndex) increases(i.e., the lower cell index has higher priority).

In another example, the CSI report priority can be based on the CSIcomponent, where RI and wideband PMI reporting have a higher prioritythan CQI reporting, and wideband CQI reporting has a higher prioritythan subband CQI reporting. RI can have a higher priority because RI canprovide general information about a network channel conditions. In anexample, PMI and CQI can be dependent on RI. Wideband CQI can havehigher priority than subband CQI, because wideband CQI can providegeneral quality information about a channel or to a worst case scenarioof the channel, whereas the subband CQI provides narrower subbandchannel quality information.

In an example, additional CSI reports can be generated in a CoordinatedMultiPoint (CoMP) system. Additional criteria for dropping CSI reportsmay be used in a CoMP system. A CoMP system (also known as multi-eNodeBmultiple input multiple output [MIMO]) can be used to improveinterference mitigation. At least four basic scenarios can be used forCoMP operation.

FIG. 7A illustrates an example of a coordination area 308 (outlined witha bold line) of an intra-site CoMP system in a homogenous network, whichcan illustrate LTE CoMP scenario 1. Each node 310A and 312B-G can servemultiple cells (or sectors) 320A-G, 322A-G, and 324A-G. The cell can bea logical definition generated by the node or geographic transmissionarea or sub-area (within a total coverage area) covered by the node,which can include a specific cell identification (ID) that defines theparameters for the cell, such as control channels, reference signals,and component carriers (CC) frequencies. By coordinating transmissionamong multiple cells, interference from other cells can be reduced andthe received power of the desired signal can be increased. The nodesoutside the CoMP system can be non-cooperating nodes 312B-G. In anexample, the CoMP system can be illustrated as a plurality ofcooperating nodes (not shown) surrounded by a plurality ofnon-cooperating nodes.

FIG. 7B illustrates an example of an inter-site CoMP system with highhigh power remote radio heads (RRHs) in a homogenous network, which canillustrate LTE CoMP scenario 2. A coordination area 306 (outlined with abold line) can include eNBs 310A and RRHs 314H-M, where each RRH can beconfigured to communicate with the eNB via a backhaul link (optical orwired link). The cooperating nodes can include eNBs and RRHs. In a CoMPsystem, the nodes can be grouped together as cooperating nodes inadjacent cells, where the cooperating nodes from multiple cells cantransmit signals to the wireless device 302 and receive signals from thewireless device. The cooperating nodes can coordinatetransmission/reception of signals from/to the wireless device 302 (e.g.,UE). The cooperating node of each CoMP system can be included in acoordinating set. A CSI report may be generated on a CSI process basedon transmissions from each coordinating set.

FIG. 7C illustrates an example of a CoMP system with low power nodes(LPNs) in a macro cell coverage area. FIG. 7C can illustrate LTE CoMPscenarios 3 and 4. In the intra-site CoMP example illustrated in FIG.7C, LPNs (or RRHs) of a macro node 310A may be located at differentlocations in space, and CoMP coordination may be within a singlemacrocell. A coordination area 304 can include eNBs 310A and LPNs380N-S, where each LPN can be configured to communicate with the eNB viaa backhaul link 332 (optical or wired link). A cell 326A of a macro nodemay be further sub-divided into sub-cells 330N-S. LPNs (or RRHs) 380N-Smay transmit and receive signals for a sub-cell. A wireless device 302can be on a sub-cell edge (or cell-edge) and intra-site CoMPcoordination can occur between the LPNs (or RRHs) or between the eNB andthe LPNs. In CoMP scenario 3, the low power RRHs providingtransmission/reception points within the macrocell coverage area canhave different cell IDs from the macro cell. In CoMP scenario 4, the lowpower RRHs providing transmission/reception points within the macrocellcoverage area can have a same cell ID as the macro cell.

Downlink (DL) CoMP transmission can be divided into two categories:coordinated scheduling or coordinated beamforming (CS/CB or CS/CBF), andjoint processing or joint transmission (JP/JT). With CS/CB, a givensubframe can be transmitted from one cell to a given mobilecommunication device (UE), and the scheduling, including coordinatedbeamforming, is dynamically coordinated between the cells in order tocontrol and/or reduce the interference between different transmissions.For joint processing, joint transmission can be performed by multiplecells to a mobile communication device (UE), in which multiple nodestransmit at the same time using the same time and frequency radioresources and dynamic cell selection. Two methods can be used for jointtransmission: non-coherent transmission, which uses soft-combiningreception of the OFDM signal; and coherent transmission, which performsprecoding between cells for in-phase combining at the receiver. Bycoordinating and combining signals from multiple antennas, CoMP, allowsmobile users to enjoy consistent performance and quality forhigh-bandwidth services whether the mobile user is close to the centerof a cell or at the outer edges of the cell.

Even with a single serving cell (i.e., single component carrier (CC)scenario), multiple periodic CSI reports may be transmitted for DL CoMP.The PUCCH report can define the format and uplink resources on which CSIcan be provided, i.e., the PUCCH report configuration can define how totransmit the CSI feedback. For CoMP operations, measuring the CSI can bedefined by a “CoMP CSI process”, which can include a configuration of achannel and interference part. Therefore, different CSI reports can beassociated with different processes. For example, the CoMP CSImeasurement associated with one CoMP CSI process can be transmittedusing periodic or aperiodic feedback modes.

The multiple periodic CSI processes can be configured by the networkusing certain IDs or index numbers in order to facilitate the multipleperiodic CSI feedbacks. As used herein, the CSI process index(CSIProcessIndex or CSIProcessID) refers to such realization of multipleperiodic CSI processes. For example, if a serving cell (e.g., servingnode) configures three periodic CSI processes, the network can configurethree CSI periodic processes and the CSIProcessIndex can be numbered as0, 1, and 2. Each periodic CSI process can be configured by RRCsignaling independently.

In legacy LTE, only one periodic CSI report may be transmitted by PUCCHformat 2, 2a, or 2b. In a case, where more than one periodic CSItransmission coincides in a subframe, only one periodic CSI report maybe transmitted and the remaining periodic CSI reports may be dropped.Although the multiple periodic CSI reports can be transmitted on eitherthe PUCCH with PUCCH format 3 or the PUSCH, the maximum payload foraggregated periodic CSI can still be limited. For example, up to 22information bits can be conveyed using PUCCH format 3. Thus, if thenumber of aggregated periodic CSI bits exceeds 22 bits, the remainingCSI reports may be dropped. In an example, if PUCCH format 2 is used forperiodic CSI transmission, only one CSI process may be selected for thetransmission regardless of the capacity criterion.

Various methods can be used to determine what CSI process or CSI reportcan be dropped when the CSIProcessID is used. For illustration purposes,the PUCCH with the PUCCH format 3, which can convey multiple CSI, isassumed, however the same principle can be used in other cases, such asother PUCCH formats or PUSCH.

If aggregated periodic CSI information bits do not exceed a maximumcapacity of a certain PUCCH format (e.g., PUCCH format 2, PUCCH format3, PUSCH, or other formats), the aggregated periodic CSI can betransmitted on the corresponding PUCCH format. Otherwise (i.e., if theaggregated periodic CSI information bits exceed the maximum capacity ofthe certain PUCCH format), the periodic CSIs among the CSI processes canbe selected such that the aggregated periodic CSI payload is a largestnumber of CSI processes not more than the maximum capacity for the PUCCHformat used in the PUCCH. For example, if the number of CSI processes is5 and PUCCH format 3 is used and if the number of CSI bits is 11 foreach CSI process, the CSI for only two CSI processes may be transmittedon PUCCH format 3 and the remaining 3 CSI processes may be dropped.

Various methods can be used to determine a priority rule for droppingCSI processes and/or reports. PUCCH using PUCCH format 3 withmulti-process CSI transmission or PUCCH format 2 with a single CSIprocess can be used. For example, if the PUCCH uses PUCCH format 2 forperiodic CSI transmission, only one CSI process may be selected for thetransmission regardless of the capacity criterion.

In a method (i.e., method 1), the priority for retaining (or dropping)the CSI processes in a colliding subframe (or potentially collidingsubframe) can first be determined by a PUCCH reporting type and/or PUCCHreporting mode. A first or highest priority CSI process can be given toPUCCH reporting Types 3, 5, 6, and 2a, then a next or second priorityCSI process can be given to PUCCH reporting Types 2, 2b, 2c, and 4, thena third or last priority CSI process can be given to PUCCH reportingTypes 1 and 1a.

If the aggregated number of CSI bits still exceeds 22 bits with PUCCHformat 3 or more than one CSI process remains with PUCCH format 2, oneof two rules can be used. Using a first rule, a CQI/PMI/PTI/RI reportingpriorities among the CSI processes with a same priority of PUCCHreporting mode and/or types can be determined based on the CSI processindex (e.g., CSIProcessID). For example, a priority of a CSI process IDdecreases as the corresponding CSI process ID increases, thus a lowerCSI process ID can have a higher priority. Using a second rule, thepriority of the can be CSI process configured by RRC signaling.

In another method (i.e., method 2), a priority for retaining (ordropping) the CSI processes in a colliding subframe can be given by RRCsignaling. In an example, a maximum capacity for PUCCH format 2 can be11 bits, PUCCH format 3 can be 22 bits, and PUSCH can be 55 bits.

A priority for retaining (or dropping) the CSI reports can also bedetermined for a simultaneous usage of carrier aggregation (using aServCellIndex) and CoMP scenarios (using a CSIProcessID orCSIProcessIndex), such as transmission mode 10. The priorities fordropping CSI reports can be defined considering both a carrier and CSIprocess domain.

For example, in a method (i.e., method A), the priority for the CSIprocesses and component carrier used for dropping (or retaining) CSIreports in a colliding subframe (or potentially colliding subframe) canfirst be based on a PUCCH reporting type and/or PUCCH reporting mode. Afirst or highest priority CSI process can be given to PUCCH reportingTypes 3, 5, 6, and 2a, then a next or second priority CSI process can begiven to PUCCH reporting Types 2, 2b, 2c, and 4, then a third or lastpriority CSI process can be given to PUCCH reporting Types 1 and 1a.

If an aggregated number of CSI bits is still more than 22 with PUCCHformat 3 or more than one CSI process still remains with PUCCH format 2,one of three rules can be used. Using a first rule, a CQI/PMI/PTI/RIreporting priorities among the serving cells with the same priority ofPUCCH reporting modes and/or types can be determined based on theserving cell indices (e.g., ServCellIndex). Priority of a cell candecrease as a corresponding serving cell index increases.

If the aggregated number of CSI bits is still more than 22 with PUCCHformat 3 or more than one CSI process still remains with PUCCH format 2,the CQI/PMI/PTI/RI reporting priorities among the CSI processes with thesame priority of PUCCH reporting mode and/or types and with a sameserving cell index can be determined based on a CSI process index (e.g.,CSIProcessID or CSIProcessIndex). Priority of a CSI process index candecrease as a corresponding CSI process index increases.

Using a second rule, the CQI/PMI/PTI/RI reporting priorities among theCSI processes for each serving cell with the same priority of PUCCHreporting mode and/or types can be determined based on the CSI processindex (e.g., CSIProcessID or CSIProcessIndex). Priority of a CSI processindex can decrease as a corresponding CSI process index increases.

If the aggregated number of CSI bits is still more than 22 with PUCCHformat 3 or more than one CSI process still remains with PUCCH format 2,the CQI/PMI/PTI/RI reporting priorities among the serving cells with thesame priority of PUCCH reporting mode and/or types and with a same CSIprocess index can be determined based on a serving cell index (e.g.,ServCellIndex). Priority of a cell can decrease as a correspondingserving cell index increases.

Using a third rule, the priority across CCs used in carrier aggregationand/or CSI process indices used in CoMP scenarios can be configured byRRC signaling.

In another method (i.e., method B), all the priorities for the CSIprocesses used in CoMP scenarios and the component carrier used incarrier aggregation can be configured by RRC signaling.

In another method (i.e., method C), the CSI process index can beuniquely defined across serving cells and CSI processes (i.e., theunique CSI process index can be combination of the CSIProcessIndex andthe ServCellIndex). In an example, the CSI process index can bedetermined and communicated via RRC signaling. For example, with twoserving cell aggregations and three CSI processes per serving cell, thetotal number of CSI processes can be uniquely defined for 6 CSIprocesses (i.e., per CSI process 0, 1, 2, 3, 4, and 5.

Using a unique CSI process index, the priority for the CSI processesused for dropping (or retaining) CSI reports in a colliding subframe (orpotentially colliding subframe) can first be based on a PUCCH reportingtype and/or PUCCH reporting mode. A first or highest priority CSIprocess can be given to PUCCH reporting Types 3, 5, 6, and 2a, then anext or second priority CSI process can be given to PUCCH reportingTypes 2, 2b, 2c, and 4, then a third or last priority CSI process can begiven to PUCCH reporting Types 1 and 1a.

If an aggregated number of CSI bits is still more than 22 with PUCCHformat 3 or more than one CSI process still remains with PUCCH format 2,the CQI/PMI/PTI/RI reporting priorities among the CSI processes with thepriority of PUCCH reporting modes and/or types can be determined basedon the CSI process index (e.g., CSIProcessID or CSIProcessIndex).Priority of a CSI process index can decrease as a corresponding CSIprocess index increases.

In another method (i.e., method D), a default CSI process index can bedefined on each serving cell. Each default CSI process index can have ahighest priority per each serving cell. Using a default CSI processindex for each serving cell, the priority for the CSI processes used fordropping (or retaining) CSI reports in a colliding subframe (orpotentially colliding subframe) can first be based on a PUCCH reportingtype and/or PUCCH reporting mode. A first or highest priority CSIprocess can be given to PUCCH reporting Types 3, 5, 6, and 2a, then anext or second priority CSI process can be given to PUCCH reportingTypes 2, 2b, 2c, and 4, then a third or last priority CSI process can begiven to PUCCH reporting Types 1 and 1a.

If an aggregated number of CSI bits is still more than 22 with PUCCHformat 3 or more than one CSI process still remains with PUCCH format 2,the CQI/PMI/PTI/RI reporting priorities among the default CSI processeswith the priority of PUCCH reporting modes and/or types can bedetermined based on the CSI process index (e.g., CSIProcessID orCSIProcessIndex). Priority of a CSI process index can decrease as acorresponding CSI process index increases.

A combination of the various methods is also contemplated.

In another example, a dropping rule for a combined carrier aggregationand CoMP scenario can be used for multiplexing of CSI and HARQ-ACK usingPUCCH format 3. Automatic Repeat reQuest is a feedback mechanism wherebya receiving terminal requests retransmission of packets which aredetected to be erroneous. Hybrid ARQ is a simultaneous combination ofAutomatic Retransmission reQuest (ARQ) and forward error correction(FEC) which can enables the overhead of error correction to be adapteddynamically depending on the channel quality. When HARQ is used and ifthe errors can be corrected by FEC then no retransmission may berequested, otherwise if the errors can be detected but not corrected, aretransmission can be requested. An ACKnowledgment (ACK) signal can betransmitted to indicate that one or more blocks of data, such as in aPDSCH, have been successfully received and decoded. HARQ-ACK/NegativeACKnowledgement (NACK or NAK) information can include feedback from areceiver to the transmitter in order to acknowledge a correct receptionof a packet or ask for a new retransmission (via NACK or NAK).

In an example, for a UE configured with PUCCH format 3 for HARQ-ACKtransmission, and for a subframe where a UE is configured to transmitHARQ-ACK transmission with periodic CSI, and for a subframe where aPUCCH format 3 resource is indicated to the UE for HARQ-ACKtransmission, the UE can transmit HARQ-ACK and a single cell periodicCSI according to the following process. No additional PUCCH format 3resources in addition to the format 3 resource may be configured forHARQ-ACK and CSI multiplexing. HARQ-ACK and periodic CSI can be jointlycoded up to 22 bits including schedule requests (SR). The serving cellfor periodic CSI reporting can be selected when the selected periodicCSI report together with HARQ-ACK feedback bits (including the SR) canfit into the PUCCH format 3 payload size. Then the periodic CSI andHARQ-ACK bits (including SR) can be transmitted, otherwise HARQ-ACK(including SR) without periodic CSI can be transmitted.

In a combined carrier aggregation and CoMP case, only one CSI report maybe selected for a combined CSI process and ACK/NACK (A/N) feedback on aPUCCH with PUCCH format 3. The selected rule of method A, B, C, and Dabove can be used to select one periodic CSI report for the combined CSIprocess and A/N on the PUCCH with PUCCH format 3.

For example, the dropping rule using method A can be represented asfollows: The priority for the CSI processes and component carrier usedfor dropping (or retaining) CSI reports in a colliding subframe (orpotentially colliding subframe) can first be based on a PUCCH reportingtype and/or PUCCH reporting mode. A first or highest priority CSIprocess can be given to PUCCH reporting Types 3, 5, 6, and 2a, then anext or second priority CSI process can be given to PUCCH reportingTypes 2, 2b, 2c, and 4, then a third or last priority CSI process can begiven to PUCCH reporting Types 1 and 1a.

If more than one CSI process still remains with PUCCH format 2, aCQI/PMI/PTI/RI reporting priorities among the CSI processes for eachserving cell with the same priority of PUCCH reporting mode and/or typescan determined based on the CSI process index (e.g., CSIProcessID orCSIProcessIndex). Priority of a CSI process index can decrease as acorresponding CSI process index increases.

Then if more than one CSI process still remains with PUCCH format 2, theCQI/PMI/PTI/RI reporting priorities among the serving cells with thesame priority of PUCCH reporting mode and/or types and with a same CSIprocess index can be determined based on a serving cell index (e.g.,ServCellIndex). Priority of a cell can decrease as a correspondingserving cell index increases.

Another example provides functionality 500 of computer circuitry of auser equipment (UE) operable to report periodic channel stateinformation (CSI) configured in a specified transmission mode, as shownin the flow chart in FIG. 8. The functionality may be implemented as amethod or the functionality may be executed as instructions on amachine, where the instructions are included on at least one computerreadable medium or one non-transitory machine readable storage medium.The computer circuitry can be configured to generate a plurality of CSIreports for transmission in a subframe for a plurality of CSI processes,wherein each CSI report corresponds to a CSI process with aCSIProcessIndex, as in block 510. The computer circuitry can be furtherconfigured to drop CSI reports corresponding to CSI processes except aCSI process with a lowest CSIProcessIndex, as in block 520. The computercircuitry can also be configured to transmit at least one CSI report forthe CSI process to an evolved Node B (eNB), as in block 530

In an example, the computer circuitry configured to drop CSI reports canbe further configured to: Determine a selected number of CSI reports totransmit based on a physical uplink control channel (PUCCH) format; anddrop the CSI reports corresponding to all CSI processes but the selectednumber of highest priority CSI reports corresponding to the CSIprocesses to avoid a CSI reporting collision in the subframe. The PUCCHformat can include a PUCCH format 2, 2a, 2b, 3 with at least a one CSIreport.

In another example, the computer circuitry configured to drop CSIreports can be further configured to drop CSI reports based on aServCellIndex except a CSI report with a lowest ServCellIndex when theCSIProcessIndexes for the CSI reports are the same. In another example,the computer circuitry can be further configured to drop at least onelower priority CSI report based on a physical uplink control channel(PUCCH) reporting type of a serving cell prior to dropping the lowerpriority CSI report based on the CSIProcessIndex. PUCCH reporting types3, 5, 6, and 2a can have a priority higher than PUCCH reporting types 1,1 a, 2, 2b, 2c, and 4, and PUCCH reporting types 2, 2b, 2c, and 4 have apriority higher than PUCCH reporting types 1 and 1 a. The highestpriority CSI report can include a lowest CSIProcessIndex. In anotherconfiguration, the computer circuitry can be further configured toassign a default CSI process with a highest priority CSI process for aserving cell corresponding to a lowest CSIProcessIndex. In anotherexample, the CSIProcessIndex can be unique for a specified CSI processand a specified serving cell. The specified transmission mode can beused for a coordinated multipoint (CoMP) configuration. In an example,the specified transmission mode can include transmission mode 10 usedfor a CoMP configuration.

Another example provides a method 600 for periodic channel stateinformation (CSI) reporting from a user equipment (UE) in a coordinatedmultipoint (CoMP) scenario, as shown in the flow chart in FIG. 9. Themethod may be executed as instructions on a machine, where theinstructions are included on at least one computer readable medium orone non-transitory machine readable storage medium. The method includesthe operation of determining at the UE, a number of CSI reports tocollide in a subframe, wherein the CSI reports include a plurality ofCSI processes, wherein each CSI report corresponds to a CSI process witha CSI process index, as in block 610. The operation of prioritizing thenumber of CSI reports, wherein a CSI process with a higher priority hasa lower CSI process index follows, as in block 620. The next operationof the method can be dropping a lower priority CSI report based in parton the CSI process index, as in block 630. The method can furtherinclude transmitting from the UE at least one highest priority CSIreport to a node, as in block 640.

The operation of prioritizing the number of CSI reports can furtherinclude prioritizing the number of CSI reports based on a channelquality indicator (CQI)/precoding matrix indicator (PMI)/rank indication(RI) reporting type, wherein CQI/PM I/RI reporting types 3, 5, 6, and 2ahave a priority higher than CQI/PMI/RI reporting types 1, 1a, 2, 2b, 2c,and 4, and CQI/PMI/RI reporting types 2, 2b, 2c, and 4 have a priorityhigher than CQI/PMI/RI reporting types 1 and 1 a. In an example, theoperation of prioritizing the number of CSI reports can further includeprioritizing the number of CSI reports based on a serving cell index ora component carrier (CC), where the CC with a higher priority has alower serving cell index, then prioritizing the number of CSI reportsbased on the CSI process index. In another example, the operation ofprioritizing the number of CSI reports can further include prioritizingthe number of CSI reports based on the CSI process index, thenprioritizing the number of CSI reports based on a serving cell index ora component carrier (CC), where the CC with a higher priority has alower serving cell index.

In another configuration, the operation of prioritizing the number ofCSI reports can further include receiving via radio resource control(RRC) signaling a priority for the CSI reports based on a CSI processindex or a component carrier (CC) for each CSI report. In anotherexample, a unique CSI process index can be assigned for a specified CSIprocess and a specified CC. In another example, the method can furtherinclude defining a default CSI process with a highest priority CSIprocess. The default CSI process can correspond to a lowest CSI processindex.

The operation of transmitting the at least one highest priority CSIreport can further include transmitting a non-colliding CSI report foreach at most 11 CSI bits available in a PUCCH format. The node caninclude a base station (BS), a Node B (NB), an evolved Node B (eNB), abaseband unit (BBU), a remote radio head (RRH), a remote radio equipment(RRE), a remote radio unit (RRU).

FIG. 10 illustrates an example node (e.g., serving node 710 andcooperation node 730) and an example wireless device 720. The node caninclude a node device 712 and 732. The node device or the node can beconfigured to communicate with the wireless device. The node device canbe configured to receive periodic channel state information (CSI)transmission configured in a specified transmission mode, such astransmission mode 10. The node device or the node can be configured tocommunicate with other nodes via a backhaul link 740 (optical or wiredlink), such as an X2 application protocol (X2AP). The node device caninclude a processing module 714 and 734 and a transceiver module 716 and736. The transceiver module can be configured to receive a periodicchannel state information (CSI) in a PUCCH. The transceiver module 716and 736 can be further configured to communicate with the coordinationnode via an X2 application protocol (X2AP). The processing module can befurther configured to process the periodic CSI reports of the PUCCH. Thenode (e.g., serving node 710 and cooperation node 730) can include abase station (BS), a Node B (NB), an evolved Node B (eNB), a basebandunit (BBU), a remote radio head (RRH), a remote radio equipment (RRE),or a remote radio unit (RRU).

The wireless device 720 can include a transceiver module 724 and aprocessing module 722. The wireless device can be configured for aperiodic channel state information (CSI) transmission configured in aspecified transmission mode, such as transmission mode used in a CoMPoperation. The processing module can be configured to generate apriority of a CSI report in a plurality of CSI reports for a subframebased on a CSI process index and a physical uplink control channel(PUCCH) reporting type, and drop a lower priority CSI report. The CSIprocess index can correspond to a downlink (DL) CoMP CSI process. Thetransceiver module can be configured to transmit at least one higherpriority CSI report to a node.

In an example, a highest priority CSI process for a serving cell cancorrespond to a lowest CSIProcessIndex. PUCCH reporting types with rankindication (RI) or wideband precoding matrix indicator (PMI) feedbackwithout channel quality indicator (CQI) feedback can have a priorityhigher than PUCCH reporting types with CQI feedback, and PUCCH reportingtypes with wideband CQI feedback can have a priority higher than PUCCHreporting with subband CQI feedback.

In a configuration, the processing module 722 can be further configuredto prioritize the CSI reports based on a serving cell index, thenprioritize the CSI reports based on a CSI process index. The CSI reportwith a lower serving cell index can have a higher priority than a CSIreport with a higher serving cell index, and the CSI report for aspecified serving cell index with a lower CSI process index can have ahigher priority than a CSI report with for the specified serving cellindex with a higher CSI process index.

In another configuration, the processing module 722 can be furtherconfigured to prioritize the CSI reports based on a CSI process index,then prioritize the CSI reports based on a serving cell index. The CSIreport with the CSI process index can have a higher priority than a CSIreport with the higher CSI process index, and the CSI report for aspecified CSI process index with a lower serving cell index can have ahigher priority than a CSI report with for the specified CSI processindex with a higher serving cell index.

In another configuration, the transceiver module 724 can be furtherconfigured to receive a priority for a CSI report with a specified CSIprocess index or a specified serving cell index via radio resourcecontrol (RRC) signaling. In an example, the processing module 722 can befurther configured to prioritize the CSI reports based on a combined CSIprocess index and serving cell index. The CSI report with a lowercombined CSI process index and serving cell index can have a higherpriority than a CSI report with a higher combined CSI process index andserving cell index. In another example, the processing module can befurther configured to assign a default CSI process with a highestpriority CSI process. The default CSI process can have a lowest CSIprocess index for a plurality of CSI processes.

In another example, the processing module 722 can be further configuredto multiplex a hybrid automatic repeat request-acknowledgement(HARQ-ACK) and a CSI report, and determine if the CSI report withHARQ-ACK feedback bits and any scheduling request (SR) fits into aphysical uplink control channel (PUCCH) format 3 payload. Thetransceiver module can be further configured to transmit the HARQ-ACKfeedback bits including any SR without the CSI report when the CSIreport with HARQ-ACK feedback bits and any SR does not fit into thePUCCH format 3 payload, and transmit the multiplexed HARQ-ACK feedbackbits including any SR with the CSI report when the CSI report withHARQ-ACK feedback bits and any SR fits into the PUCCH format 3 payload.In another configuration, the transceiver module can be furtherconfigured to transmit a number of non-colliding CSI reports for aphysical uplink control channel (PUCCH) format. Each CSI report can useat most 11 CSI bits.

FIG. 11 provides an example illustration of the wireless device, such asan user equipment (UE), a mobile station (MS), a mobile wireless device,a mobile communication device, a tablet, a handset, or other type ofwireless device. The wireless device can include one or more antennasconfigured to communicate with a node, macro node, low power node (LPN),or, transmission station, such as a base station (BS), an evolved Node B(eNB), a baseband unit (BBU), a remote radio head (RRH), a remote radioequipment (RRE), a relay station (RS), a radio equipment (RE), or othertype of wireless wide area network (WWAN) access point. The wirelessdevice can be configured to communicate using at least one wirelesscommunication standard including 3GPP LTE, WiMAX, High Speed PacketAccess (HSPA), Bluetooth, and WiFi. The wireless device can communicateusing separate antennas for each wireless communication standard orshared antennas for multiple wireless communication standards. Thewireless device can communicate in a wireless local area network (WLAN),a wireless personal area network (WPAN), and/or a WWAN.

FIG. 11 also provides an illustration of a microphone and one or morespeakers that can be used for audio input and output from the wirelessdevice. The display screen may be a liquid crystal display (LCD) screen,or other type of display screen such as an organic light emitting diode(OLED) display. The display screen can be configured as a touch screen.The touch screen may use capacitive, resistive, or another type of touchscreen technology. An application processor and a graphics processor canbe coupled to internal memory to provide processing and displaycapabilities. A non-volatile memory port can also be used to providedata input/output options to a user. The non-volatile memory port mayalso be used to expand the memory capabilities of the wireless device. Akeyboard may be integrated with the wireless device or wirelesslyconnected to the wireless device to provide additional user input. Avirtual keyboard may also be provided using the touch screen.

Various techniques, or certain aspects or portions thereof, may take theform of program code (i.e., instructions) embodied in tangible media,such as floppy diskettes, CD-ROMs, hard drives, non-transitory computerreadable storage medium, or any other machine-readable storage mediumwherein, when the program code is loaded into and executed by a machine,such as a computer, the machine becomes an apparatus for practicing thevarious techniques. Circuitry can include hardware, firmware, programcode, executable code, computer instructions, and/or software. Anon-transitory computer readable storage medium can be a computerreadable storage medium that does not include signal. In the case ofprogram code execution on programmable computers, the computing devicemay include a processor, a storage medium readable by the processor(including volatile and non-volatile memory and/or storage elements), atleast one input device, and at least one output device. The volatile andnon-volatile memory and/or storage elements may be a RAM, EPROM, flashdrive, optical drive, magnetic hard drive, solid state drive, or othermedium for storing electronic data. The node and wireless device mayalso include a transceiver module, a counter module, a processingmodule, and/or a clock module or timer module. One or more programs thatmay implement or utilize the various techniques described herein may usean application programming interface (API), reusable controls, and thelike. Such programs may be implemented in a high level procedural orobject oriented programming language to communicate with a computersystem. However, the program(s) may be implemented in assembly ormachine language, if desired. In any case, the language may be acompiled or interpreted language, and combined with hardwareimplementations.

It should be understood that many of the functional units described inthis specification have been labeled as modules, in order to moreparticularly emphasize their implementation independence. For example, amodule may be implemented as a hardware circuit comprising custom VLSIcircuits or gate arrays, off-the-shelf semiconductors such as logicchips, transistors, or other discrete components. A module may also beimplemented in programmable hardware devices such as field programmablegate arrays, programmable array logic, programmable logic devices or thelike.

Modules may also be implemented in software for execution by varioustypes of processors. An identified module of executable code may, forinstance, comprise one or more physical or logical blocks of computerinstructions, which may, for instance, be organized as an object,procedure, or function. Nevertheless, the executables of an identifiedmodule need not be physically located together, but may comprisedisparate instructions stored in different locations which, when joinedlogically together, comprise the module and achieve the stated purposefor the module.

Indeed, a module of executable code may be a single instruction, or manyinstructions, and may even be distributed over several different codesegments, among different programs, and across several memory devices.Similarly, operational data may be identified and illustrated hereinwithin modules, and may be embodied in any suitable form and organizedwithin any suitable type of data structure. The operational data may becollected as a single data set, or may be distributed over differentlocations including over different storage devices, and may exist, atleast partially, merely as electronic signals on a system or network.The modules may be passive or active, including agents operable toperform desired functions.

Reference throughout this specification to “an example” means that aparticular feature, structure, or characteristic described in connectionwith the example is included in at least one embodiment of the presentinvention. Thus, appearances of the phrases “in an example” in variousplaces throughout this specification are not necessarily all referringto the same embodiment.

As used herein, a plurality of items, structural elements, compositionalelements, and/or materials may be presented in a common list forconvenience. However, these lists should be construed as though eachmember of the list is individually identified as a separate and uniquemember. Thus, no individual member of such list should be construed as ade facto equivalent of any other member of the same list solely based ontheir presentation in a common group without indications to thecontrary. In addition, various embodiments and example of the presentinvention may be referred to herein along with alternatives for thevarious components thereof. It is understood that such embodiments,examples, and alternatives are not to be construed as defectoequivalents of one another, but are to be considered as separate andautonomous representations of the present invention.

Furthermore, the described features, structures, or characteristics maybe combined in any suitable manner in one or more embodiments. In thefollowing description, numerous specific details are provided, such asexamples of layouts, distances, network examples, etc., to provide athorough understanding of embodiments of the invention. One skilled inthe relevant art will recognize, however, that the invention can bepracticed without one or more of the specific details, or with othermethods, components, layouts, etc. In other instances, well-knownstructures, materials, or operations are not shown or described indetail to avoid obscuring aspects of the invention.

While the forgoing examples are illustrative of the principles of thepresent invention in one or more particular applications, it will beapparent to those of ordinary skill in the art that numerousmodifications in form, usage and details of implementation can be madewithout the exercise of inventive faculty, and without departing fromthe principles and concepts of the invention. Accordingly, it is notintended that the invention be limited, except as by the claims setforth below.

What is claimed is:
 1. An apparatus of a user equipment (UE) to report periodic channel state information (CSI), the apparatus comprising: memory; one or more processors configured to: generate a plurality of CSI reports for serving cells for transmission in a subframe, wherein each CSI report corresponds to a physical uplink control channel (PUCCH) reporting type among a plurality of CSI processes having a CSI process index (CSIProcessIndex) and a serving cell index (ServCellIndex) among a plurality of ServCellIndexes; determine a first collision between CSI reports, among the plurality of CSI reports, having PUCCH reporting types with equal priorities in the subframe and, upon determining the first collision, drop CSI reports corresponding to all CSI processes except a CSI process having the lowest CSIProcessIndex; determine a second collision between CSI reports, after determining the first collision, among retained ones of the plurality of CSI reports, having CSIProcessIndexes with equal priorities in the subframe and, upon determining the second collision, drop the CSI reports corresponding to all ServCellIndexes except a CSI report with the lowest ServCellIndex; determine whether the at least one non-colliding CSI report multiplexed with hybrid automatic repeat request-acknowledgement (HARQ-ACK) feedback bits and any scheduling request (SR)fits into a payload of a PUCCH format 3; and a transceiver configured to: transmit the at least one non-colliding CSI report and the HARQ-ACK feedback bits from the UE to the eNodeB when the at least one non-colliding CSI report multiplexed with the HARQ-ACK feedback bits and any SR fits into the payload of the PUCCH format 3; and transmit the HARQ-ACK feedback bits including any SR without the at least one non-colliding CSI report when the at least one non-colliding CSI report with HARQ-ACK feedback bits and any SR does not fit into the payload of the PUCCH format
 3. 2. The apparatus of claim 1, wherein the UE is configured to operate in a transmission mode (TM) 10 used in a coordinated multipoint (CoMP) scenario and carrier aggregation (CA) configuration.
 3. The apparatus of claim 1, wherein a CSI report for a specific ServCellIndex with a lower CSIProcessIndex has a higher priority than a CSI report for the specific ServCellIndex with a CSIProcessIndex higher than the lower CSIProcessIndex.
 4. The apparatus of claim 1, wherein a CSI report for a specific CSIProcessIndex with a lower ServCellIndex has a higher priority than a CSI report for the specific CSIProcessIndex with a ServCellIndex that is higher than the lower ServCellIndex.
 5. The apparatus of claim 1, wherein: the PUCCH reporting type is one of PUCCH reporting types 1, 1a, 2, 2b, 2c, or 4; or the PUCCH reporting type is one of PUCCH reporting types 3, 5, or
 6. 6. A user equipment (UE) operable to report periodic channel state information (CSI), the UE comprising: one or more antennas to communicate with an evolved Node B (eNB); an application processor configured to: generate a plurality of CSI reports for serving cells for transmission in a subframe, wherein each CSI report corresponds to a physical uplink control channel (PUCCH) reporting type among a plurality of CSI processes having a CSI process index (CSIProcessIndex) and a serving cell index (ServCellIndex) among a plurality of ServCellIndexes; determine a first collision between CSI reports, among the plurality of CSI reports, having PUCCH reporting types with equal priorities in the subframe and, upon determining the first collision, drop CSI reports corresponding to all CSI processes except a CSI process having the lowest CSIProcessIndex; determine a second collision between CSI reports, after determining the first collision, among retained ones of the plurality of CSI reports, having CSIProcessIndexes with equal priorities in the subframe and, upon determining the second collision, drop the CSI reports corresponding to all ServCellIndexes except a CSI report with the lowest ServCellIndex; prepare at least one non-colliding CSI report from among CSI reports that are not dropped; and determine whether the at least one non-colliding CSI report with hybrid automatic repeat request-acknowledgement (HARQ-ACK) feedback bits and any scheduling request (SR)fits into a payload of the PUCCH format 3; and a transceiver configured to: transmit the at least one non-colliding CSI report and the HARQ-ACK feedback bits and any SR from the UE to the eNodeB when the at least one non-colliding CSI report multiplexed with the HARQ-ACK feedback bits and any SR fits into the payload of the PUCCH format 3; and transmit the HARQ-ACK feedback bits including any SR without the at least one non-colliding CSI report when the at least one non-colliding CSI report with HARQ-ACK feedback bits and any SR does not fit into the payload of the PUCCH format
 3. 7. The UE of claim 6, wherein the UE is configured to operate in a transmission mode (TM) 10 used in a coordinated multipoint (CoMP) scenario and carrier aggregation (CA) configuration.
 8. The UE of claim 6, wherein a CSI report for a specific ServCellIndex with a lower CSIProcessIndex has a higher priority than a CSI report for the specific ServCellIndex with a CSIProcessIndex higher than the lower CSIProcessIndex.
 9. The UE of claim 6, wherein a CSI report for a specific CSIProcessIndex with a lower ServCellIndex has a higher priority than a CSI report for the specific CSIProcessIndex with a ServCellIndex that is higher than the lower ServCellIndex.
 10. The UE of claim 6, wherein: the PUCCH reporting type is one of PUCCH reporting types 1, 1a, 2, 2b, 2c, or 4; or the PUCCH reporting type is one of PUCCH reporting types 3, 5, or
 6. 11. The UE of claim 6, wherein the UE includes at least one of an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, an application processor, internal memory, a non-volatile memory port, and combinations thereof.
 12. At least one non-transitory machine readable storage medium having instructions embodied thereon for reporting periodic channel state information (CSI), the instructions when executed perform the following: generating, using one or more processors of a user equipment (UE), a plurality of CSI reports for serving cells for transmission in a subframe, wherein each CSI report corresponds to a physical uplink control channel (PUCCH) reporting type among a plurality of CSI processes having a CSI process index (CSIProcessIndex) and a serving cell index (ServCellIndex) among a plurality of ServCellIndexes; determining, using the one or more processors of the UE, a first collision between CSI reports, among the plurality of CSI reports, having PUCCH reporting types with equal priorities in the subframe and, upon determining the first collision, drop CSI reports corresponding to all CSI processes except a CSI process having the lowest CSIProcessIndex; determining, using the one or more processors of the UE, a second collision between CSI reports, after determining the first collision, among retained ones of the plurality of CSI reports, having CSIProcessIndexes with equal priorities in the subframe and, upon determining the second collision, drop the CSI reports corresponding to all ServCellIndexes except a CSI report with the lowest ServCellIndex; preparing, using the one or more processors of the UE, at least one non-colliding CSI report from among CSI reports that are not dropped; determine whether the at least one non-colliding CSI report with hybrid automatic repeat request-acknowledge (HARQ-ACK) feedback bits and any scheduling request (SR) fits into a payload of the PUCCH format 3; encoding the at least one non-colliding CSI report and the HARQ-ACK feedback bits for transmission to the eNodeB when the at least one non-colliding CSI report multiplexed with the HARQ-ACK feedback bits and any SR fits into the payload of the PUCCH format 3; and encoding the HARQ-ACK feedback bits including any SR without the at least one non-colliding CSI report when the at least one non-colliding CSI report with HARQ-ACK feedback bits and any SR does not fit into the payload of the PUCCH format
 3. 13. The at least one non-transitory machine readable storage medium of claim 12, wherein the UE is configured to operate in a transmission mode (TM) 10 used in a coordinated multipoint (CoMP) scenario and carrier aggregation (CA) configuration.
 14. The at least one non-transitory machine readable storage medium of claim 12, wherein a CSI report for a specific ServCellIndex with a lower CSIProcessIndex has a higher priority than a CSI report for the specific ServCellIndex with a CSIProcessIndex higher than the lower CSIProcessIndex.
 15. The at least one non-transitory machine readable storage medium of claim 12, wherein a CSI report for a specific CSIProcessIndex with a lower ServCellIndex has a higher priority than a CSI report for the specific CSIProcessIndex with a ServCellIndex that is higher than the lower ServCellIndex. 